This is a ROM-resident floppy disk operating system that sits at $B800$BFFF. 

loader41 is a small floppy disk operating system that sits in ROM at $B800$BFFF: a file system with a byte-stream interface on top of a Western Digital floppy controller. 
It uses MONA's zero-page pointers ($EF/$F0, $F5/$F6, $F7/$F8), so I gave them MONAs names in the source.

LOADER41.ASM is complete disassembled source. When I assemble it, the result matches loader41.bin byte for byte, all 2048 bytes. Ive attached the converted loader41.bin as well.

Hardware it drives

Controller: a WD1771/179x-type chip at $BFC0$BFC3 (command/status, track, sector, data). The commands it uses fit that family: $08 restore, $14 seek, $88 read sector, $A8 write sector and $C4 read address.
Drive select: a latch at $BFC4 that selects the drive and switches the motor on. Two drives are supported (DRVTAB holds $62 and $A2).
Disk format: 40 tracks, 16 sectors per track, 128-byte sectors, so about 80 KB per disk.

File system (my reading, not documented anywhere)

Directory: on track 0, read into $B500. Entries are 12 bytes, ten per sector. Each has a 6-character name, a flag bit in byte 6 (probably write-protect) and start and size information.
Workspace: RAM at $B400$B4FF, with sector buffers at $B600 (read) and $B700 (write). The read and write channels can be open at the same time.
Startup: at power-on it seeks to track 0 and times the index pulses to wait until the drive is up to speed. To find the current track it uses the read-address command.

How a program uses it

Jump table at $B800:
COLD resets the open-file flags.
DOS executes a command.
EOFTST tests for end of file.
RDBYTE reads the next byte from the open file.
WRBYTE writes a byte to the open file.
Calling a command: put the command code in $B480, the drive in $B481 and the filename in $B482$B487, then call DOS.
Command codes: $E0$E9 and $F0$F9. For most of them, an even code means the read channel and an odd code means the write channel.
$F0/$F1 probably open a file.
$E0/$E1 close it, flushing the last sector on write.
$F2/$F3 look like open at a record position.
$F6/$F8 write a directory entry, with $F8 setting the flag bit.
$F7 and $F9 jump to $EE4E and $EE19. So theres another ROM at $E000 thats part of this package; if you have it, I can do that one too.
Errors: an error puts the stack back where it was at the call and returns with a code in $B48B. The codes I could work out:
Code	Meaning
1	file not found
3	position beyond the end of the file
5	disk full
7	unknown command
8	write-protected disk
9	channel already open or directory full
Code 2 comes from read or write failures. Code 3 is also given for restore or seek failures.

About the source

Labels: none of the names are original; I chose them. The I/O and RAM equates (FDCCMD, CMD, DRIVE, FNAME, ERROR and so on), the jump-table names and the table names come from what the code does. Everything else is L_xxxx, named after its address.
Skip trick: in four places the code jumps into the middle of a BIT abs instruction to skip the next two bytes. The source writes those as .BYTE $2C followed by the hidden instruction.
Command table: dispatch uses the push-the-address-then-RTS trick, so the table entries are written as .WORD target-1.
$BFC0$BFFF: this is where the controller registers sit, so the ROM bytes there are never seen by the CPU. I kept them as .BYTE lines only so the image matches the dump exactly.
Comments: the source has none, since there was no original listing for this one.